Skunkware 5/Skunkware 5.iso/tls/tls036.1.Z/tls036.1/usr/man/cat.SMT/fdfit.SMT.z/fdfit.SMT

Text File | 1992-09-15 | 14.1 KB | 361 lines

 fdfit(SMT)                           .                            fdfit(SMT)



 _N_a_m_e

    fdfit - fits file archives onto media volumes

 _S_y_n_t_a_x

    ffddffiitt [_oooo_pppp_tttt_iiii_oooo_nnnn_ssss] ... _ssss_iiii_zzzz_eeee _pppp_aaaa_cccc_kkkk_aaaa_gggg_eeee_ssss _...._...._....

 _O_p_t_i_o_n_s


    --ff _ffff_oooo_rrrr_mmmm_aaaa_tttt The files are saved in a _ffff_oooo_rrrr_mmmm_aaaa_tttt archive.  The default _ffff_oooo_rrrr_mmmm_aaaa_tttt is
              the first listed in /_e_t_c/_f_d_f_o_r_m_a_t_s, and by convention is
              ttaarr(C).  A number may be appended to _ffff_oooo_rrrr_mmmm_aaaa_tttt; the meaning of
              that number depends on _ffff_oooo_rrrr_mmmm_aaaa_tttt but usually indicates the block-
              ing factor.  For example, a _ffff_oooo_rrrr_mmmm_aaaa_tttt of ttaarr2200 means that ttaarr is
              blocked at 20.

              The archive formats listed in /_e_t_c/_f_d_f_o_r_m_a_t_s include:

              ttaarr[bb]    ttaarr format, blocked bb

              ccppiioo [cc][BB]
                        ccppiioo format, either binary or ASCII (cc), and either
                        default blocking or 5120-byte records (BB)

              aarr        aarr(CP) archive

              dddd[_oooo_bbbb_ssss]   dddd(C) format, with an output record size of _oooo_bbbb_ssss bytes

    --oo _pppp_aaaa_tttt_tttt_eeee_rrrr_nnnn
              _pppp_aaaa_tttt_tttt_eeee_rrrr_nnnn is the naming convention used for the output files.
              Every time ``#'' appears in _pppp_aaaa_tttt_tttt_eeee_rrrr_nnnn, the two-digit number of
              the volume is substituted.  There must be at least one ``#'' in
              _pppp_aaaa_tttt_tttt_eeee_rrrr_nnnn; the default is ``#.fd''.  Volumes are numbered start-
              ing at one (``01''); if there are any files too big to fit on a
              single volume, these are listed as volume ``00''.  Any old
              files following the naming _pppp_aaaa_tttt_tttt_eeee_rrrr_nnnn are removed.

    --qq        does not complain about absolute pathnames, even if they are
              not recommended for _ffff_oooo_rrrr_mmmm_aaaa_tttt

    --ee        exits successfully even if some of the files in the packages
              could not be found

    --vv        prints, on the standard output, a table summarizing the
              arrangement chosen and the efficiency achieved

    --FF _ffff_oooo_rrrr_mmmm_aaaa_tttt_ssss_ffff_iiii_llll_eeee
              alternate list of _ffff_oooo_rrrr_mmmm_aaaa_tttt descriptions; the default is
              /_e_t_c/_f_d_f_o_r_m_a_t_s

    --OO _aaaa_llll_gggg_oooo_rrrr_iiii_tttt_hhhh_mmmm
              specifies the default arranging _aaaa_llll_gggg_oooo_rrrr_iiii_tttt_hhhh_mmmm:

              nn              Next file.  If the next file in the input list
                             does not fit on the current volume, the current
                             volume is finished and a new volume started.
                             This preserves the order of the files but may
                             waste volumes.

              ff              First fit.  The first file that fits on the
                             current volume is chosen for that volume.  Only
                             when none of the files fit is the current volume
                             finished and a new volume started.

              bb              Biggest fit.  Similar to _aaaa_llll_gggg_oooo_rrrr_iiii_tttt_hhhh_mmmm ff, except
                             that the largest file possible is chosen.

              ss              Smallest fit.  Identical to _aaaa_llll_gggg_oooo_rrrr_iiii_tttt_hhhh_mmmm bb, except
                             that the smallest file possible is chosen.

              ::              Each package starts on a new volume.

              ++              After one package is finished, the next package
                             may be started on that volume.
              Note that the default _aaaa_llll_gggg_oooo_rrrr_iiii_tttt_hhhh_mmmm can be overridden on a
              package-by-package basis.  The initial default _aaaa_llll_gggg_oooo_rrrr_iiii_tttt_hhhh_mmmm is
              ``f+''.

    --cc        checks to see if each package fits on exactly one volume.  No
              output files are generated unless an explicit _pppp_aaaa_tttt_tttt_eeee_rrrr_nnnn is given,
              and all _aaaa_llll_gggg_oooo_rrrr_iiii_tttt_hhhh_mmmm_ssss are ignored.

    --ll _llll_aaaa_bbbb_eeee_llll  The file named _llll_aaaa_bbbb_eeee_llll (which is a pattern similar to --oo _pppp_aaaa_tttt_tttt_eeee_rrrr_nnnn)
              is the first file on each volume.  If _llll_aaaa_bbbb_eeee_llll does not exist, it
              is created with zero length and a mode of 0444 (only read
              access for all).  If _llll_aaaa_bbbb_eeee_llll does exist, it must be a regular
              file; whatever size _llll_aaaa_bbbb_eeee_llll has is used.

    _ssss_iiii_zzzz_eeee, which must be given after all _oooo_pppp_tttt_iiii_oooo_nnnn_ssss, is the size of each volume
    in bytes.  A suffix of ``k'' multiplies the number by 1024, ``b'' by 512,
    and ``w'' by 2.

    _pppp_aaaa_cccc_kkkk_aaaa_gggg_eeee_ssss are collections of files that are to be arranged as an indivisi-
    ble unit.  If the ``:'' _aaaa_llll_gggg_oooo_rrrr_iiii_tttt_hhhh_mmmm modifier is in effect, each package
    starts a new volume; otherwise (``+'') packages may share volumes.  At
    least one _pppp_aaaa_cccc_kkkk_aaaa_gggg_eeee must be described after _ssss_iiii_zzzz_eeee:

    _ffff_iiii_llll_eeee      The files in this package are listed in _ffff_iiii_llll_eeee; the package has
              the default _aaaa_llll_gggg_oooo_rrrr_iiii_tttt_hhhh_mmmm applied to it.  A _ffff_iiii_llll_eeee of ``-'' means the
              standard input.

    --pp [_aaaa_llll_gggg_oooo_rrrr_iiii_tttt_hhhh_mmmm] _ffff_iiii_llll_eeee
              Same as above, except that _aaaa_llll_gggg_oooo_rrrr_iiii_tttt_hhhh_mmmm (if given) is used instead
              of the default.

    --PP [_aaaa_llll_gggg_oooo_rrrr_iiii_tttt_hhhh_mmmm] _ffff_iiii_llll_eeee_ssss _...._...._....
              Similar to --pp, except that the named _ffff_iiii_llll_eeee_ssss are the package.


 _D_e_s_c_r_i_p_t_i_o_n

    ffddffiitt tries to arrange groups (``packages'') of files onto the fewest
    number of media volumes while avoiding splitting any file across two or
    more media volumes.  Packages are not intermixed, and all links to a file
    within a package are placed on the same volume.  Each volume has a capa-
    city of  _ssss_iiii_zzzz_eeee bytes, and is written in a specified  _ffff_oooo_rrrr_mmmm_aaaa_tttt, such as
    ttaarr(C) or ccppiioo(C).

    An arbitrary number of packages may be given.  The packages are dealt
    with on a one-by-one basis, with each package being completely arranged
    before the next package is started.  The _aaaa_llll_gggg_oooo_rrrr_iiii_tttt_hhhh_mmmm used to arrange each
    package may be individually specified.  Whether or not a package can
    start on the same volume that holds the end of the previous package may
    also be specified.

    The output of ffddffiitt is a series of files; the first file lists the files
    that belong on volume one, the second lists the files for volume two, and
    so on (up to a limit of 100 volumes).

 _N_o_t_e_s

    Links in packages arranged by the ``n'' algorithm are usually scrambled.

    No effort is made to ensure that directories occur in the arrangement
    before any files contained in them.

    Some formats are inherently non-portable.  Furthermore, some of the port-
    able formats, such as ttaarr, have slightly different overheads on different
    machines.

    Under obscure conditions, linked files in large packages may cause infin-
    ite looping.

 _F_o_r_m_a_t _f_i_l_e

    An ffddffoorrmmaattss file describes a file archiving format to ffddffiitt(SMT).  ffddffiitt
    only understands distributed dictionary archives, such as ttaarr(C),
    ccppiioo(C), and aarr(CP).

    Each line in an ffddffoorrmmaattss file describes a separate _ffff_oooo_rrrr_mmmm_aaaa_tttt.  The format
    is in the form:

       ffddffoorrmmaattss _vvvv_oooo_llll_hhhh_dddd_rrrr _ffff_iiii_llll_hhhh_dddd_rrrr _vvvv_oooo_llll_bbbb_llll_kkkk _ffff_iiii_llll_rrrr_nnnn_dddd [++] [//] [_tttt_yyyy_pppp_eeee[_ssss_iiii_zzzz_eeee]]...

    Empty lines, and lines beginning with ``*'', are ignored.

    The first field, _ffff_oooo_rrrr_mmmm_aaaa_tttt, names the archive being described.  _ffff_oooo_rrrr_mmmm_aaaa_tttt is an
    alphabetic name; no digits or non-letters are allowed.

    The next four fields are decimal numbers giving the critical values:

    _vvvv_oooo_llll_hhhh_dddd_rrrr    the overhead for each volume (floppy).  This is the sum of the
              sizes of the volume header and trailer blocks.

    _ffff_iiii_llll_hhhh_dddd_rrrr    the overhead for each file (element) in the archive.  This is
              the sum of the sizes of the element header and trailer blocks,
              and may be dependent on the length of the file's name.  If so,
              a ``+'' should be specified in the miscellaneous fields section
              at the end of the line.

    _vvvv_oooo_llll_bbbb_llll_kkkk    the volume blocking factor.  The number of bytes written to
              each volume is always a multiple of this size.
    _ffff_iiii_llll_rrrr_nnnn_dddd    the file rounding boundary.  Each element in the archive, with
              its header and trailer, is rounded up to the next such bound-
              ary.

    Each of these values may have a suffixed unit of ``w'', ``b'', or ``k'',
    indicating multiplication of the number by 2, 512, and 1024, respec-
    tively.

    In addition, each number may be prefixed by ``#''.  This causes the num-
    ber suffixed to _ffff_oooo_rrrr_mmmm_aaaa_tttt, as specified by the user with the --ff _ffff_oooo_rrrr_mmmm_aaaa_tttt flag
    to ffddffiitt, to be used instead of the value given in ffddffoorrmmaattss.  If the
    value in ffddffoorrmmaattss is suffixed with a unit, the value from --ff _ffff_oooo_rrrr_mmmm_aaaa_tttt is
    multiplied as indicated, ignoring any unit the user specified.  But when
    ffddffoorrmmaattss does not indicate a unit, any unit indicated with --ff _ffff_oooo_rrrr_mmmm_aaaa_tttt is
    used.

    After the four values is a miscellaneous information section.  If this
    contains a ``+'', then the length of a file's name must be added to that
    file's _ffff_iiii_llll_hhhh_dddd_rrrr.  A ``/'' says that absolute pathnames are not a problem in
    this _ffff_oooo_rrrr_mmmm_aaaa_tttt.

    The other fields in the miscellaneous section are a single character _tttt_yyyy_pppp_eeee
    optionally followed by a _ssss_iiii_zzzz_eeee value.  The _tttt_yyyy_pppp_eeee indicates that a special
    file is correctly saved in a ffoorrmmaatt archive:

         bb    block special device

         cc    character special device

         dd    directory

         nn    name space entry, such as semaphores and shared data regions

         pp    named pipes (FIFO's)

         &&    links to previously saved files

    If _ssss_iiii_zzzz_eeee is a number (which may have a unit suffix), the _tttt_yyyy_pppp_eeee special file
    is always saved as if it were _ssss_iiii_zzzz_eeee bytes long.  A _ssss_iiii_zzzz_eeee of ``#'' uses the
    actual file size obtained from ssttaatt(S).  Otherwise, when no _ssss_iiii_zzzz_eeee is
    specified, zero (0) is assumed; the special file is completely described
    by the element header and trailer blocks.

 _F_o_r_m_a_t _f_i_l_e _n_o_t_e_s

    Unpredictable results happen when both ``+'' and ``&'' are specified.

    The meaning of ``/'' is subjective; most archiving programs archive abso-
    lute pathnames, but the behavior on extraction is undesirable (extreme
    measures like cchhrroooott(C) must be employed).

 _S_e_e _a_l_s_o

    aarr(CP), ccppiioo(C), dddd(C), ttaarr(C)